Content delivery network request handling mechanism with cached control information

ABSTRACT

Described herein are improved systems, methods, and devices for delivering and managing metadata in a distributed computing platform such as a content delivery network (CDN) so as to configure content servers to handle client requests. The teachings hereof provide, among other things, scalable and configurable solutions for delivering and managing metadata, preferably by leveraging dynamically obtained control information. For example, in one embodiment, a given content server may store metadata, e.g., in a configuration file, that references dynamic, late-bound control information for use in satisfying dependencies. This dynamic control information can be requested by the CDN content server, typically from a remote host, when needed to parse and execute the metadata.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/135,148, filed Dec. 19, 2013, which is a non-provisional of and claims the benefit of priority of both U.S. Application No. 61/740,598, filed Dec. 21, 2012, and U.S. Application No. 61/740,627, filed Dec. 21, 2012. The contents of all the foregoing applications are hereby incorporated by reference for all purposes.

This patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND Technical Field

This application relates generally to distributed data processing systems and to the delivery of content over computer networks.

Brief Description of the Related Art

Distributed computer systems are known in the art. One such distributed computer system is a “content delivery network” or “CDN” that is operated and managed by a service provider. The service provider typically provides the content delivery service on behalf of third parties. A “distributed system” of this type typically refers to a collection of autonomous computers linked by a network or networks, together with the software, systems, protocols and techniques designed to facilitate various services, such as content delivery or the support of outsourced site infrastructure. Typically, “content delivery” refers to the storage, caching, or transmission of content—such as web pages, streaming media and applications—on behalf of content providers, and ancillary technologies used therewith including, without limitation, DNS query handling, provisioning, data monitoring and reporting, content targeting, personalization, and business intelligence.

In a known system such as that shown in FIG. 1, a distributed computer system 100 is configured as a content delivery network (CDN) and is assumed to have a set of machines distributed around the Internet. Typically, most of the machines are configured as CDN content servers 102. Such machines may be located near the edge of the Internet, i.e., at or adjacent end user access networks. A network operations command center (NOCC) 104 may be used to administer and manage operations of the various machines in the system. Third party sites affiliated with content providers, such as web site hosted at origin server 106, offload delivery of content (e.g., HTML, embedded page objects, streaming media, software downloads, and the like) to the distributed computer system 100 and, in particular, to the servers 102 (which are sometimes referred to as “edge” servers in light of the possibility that they are near an “edge” of the Internet). Such servers 102 may be grouped together into a point of presence (POP) 107.

Typically, content providers offload their content delivery by aliasing (e.g., by a DNS CNAME) given content provider domains or sub-domains to domains that are managed by the service provider's authoritative domain name service. End user client machines 122 that desire such content may be directed to the distributed computer system to obtain that content more reliably and efficiently. The CDN's servers 102 respond to the client requests, for example by obtaining requested content from a local cache, from another CDN server 102, from the origin server 106, or other source.

Although not shown in detail in FIG. 1, the distributed computer system may also include other infrastructure, such as a distributed data collection system 108 that collects usage and other data from the content servers, aggregates that data across a region or set of regions, and passes that data to other back-end systems 110, 112, 114 and 116 to facilitate monitoring, logging, alerts, billing, management and other operational and administrative functions. Distributed network agents 118 monitor the network as well as the server loads and provide network, traffic and load data to a domain name system (DNS) query handling mechanism 115, which is authoritative for content domains being managed by the CDN. A distributed data transport mechanism 120 may be used to distribute control information (e.g., metadata to manage content, to facilitate load balancing, and the like) to the servers 102.

As illustrated in FIG. 2, a given machine 200 in the CDN (e.g., a given CDN server 102) comprises commodity hardware (e.g., an Intel processor) 202 running an operating system kernel (such as Linux® or variant) 204 that supports one or more applications 206. To facilitate content delivery services, for example, given machines typically run a set of applications, such as an HTTP proxy server 207, a name server 208, a local monitoring process 210, a distributed data collection process 212, and the like. The HTTP proxy 207 (sometimes referred to herein as a global host or “ghost”) typically includes a manager process for managing a cache and delivery of content from the machine. For streaming media, the machine typically includes one or more media servers, such as a Windows® Media Server (WMS) or Flash® server, as required by the supported media formats.

The machine shown in FIG. 2 may be configured to provide one or more extended content delivery features, preferably on a domain-specific, content-provider-specific basis, preferably using configuration files that are distributed to the CDN servers 102 using a configuration system. A given configuration file preferably is extensible markup language (XML)-based and includes a set of content handling rules and directives that facilitate one or more advanced content handling features. The configuration file may be delivered to a CDN server 102 via the data transport mechanism 120. U.S. Pat. No. 7,240,100, the contents of which are hereby incorporated by reference, illustrate a useful infrastructure for delivering and managing CDN server content control information and this and other content server control information (referred to as “metadata”) can be provisioned by the CDN service provider itself, or (via an extranet or the like) the content provider customer who operates the origin server 106.

The contents of U.S. Pat. No. 7,111,057, titled “Method and system for purging content from a content delivery network,” are hereby incorporated by reference.

In a typical operation, a content provider identifies a content provider domain or sub-domain that it desires to have served by the CDN. The CDN service provider associates (e.g., via a canonical name, or CNAME, or other aliasing technique) the content provider domain with a CDN hostname, and the CDN provider then provides that CDN hostname to the content provider. When a DNS query to the content provider domain or sub-domain is received at the content provider's domain name servers, those servers respond by returning the CDN hostname. That network hostname points to the CDN, and that hostname is then resolved through the CDN name service. To that end, the CDN name service returns one or more IP addresses. The requesting client browser then makes a content request (e.g., via HTTP or HTTPS) to a CDN server associated with the IP address. The request includes a host header that includes the original content provider domain or sub-domain. Upon receipt of the request with the host header, the server checks its configuration file to determine whether the content domain or sub-domain requested is actually being handled by the CDN. If so, the server applies its content handling rules and directives for that domain or sub-domain as specified in the configuration. As noted above, these content handling rules and directives may be located within an XML-based “metadata” configuration file.

As an overlay, the CDN resources may be used to facilitate wide area network (WAN) acceleration services between enterprise data centers (which may be privately managed) and third party software-as-a-service (SaaS) providers.

CDN customers may subscribe to a “behind the firewall” managed service product to accelerate Intranet web applications that are hosted behind the customer's enterprise firewall, as well as to accelerate web applications that bridge between their users behind the firewall to an application hosted in the Internet ‘cloud’ (e.g., from a SaaS provider). To accomplish these two use cases, CDN software may execute on machines (potentially virtual machines running on customer hardware) hosted in one or more customer data centers, and on machines hosted in remote “branch offices.” The CDN software executing in the customer data center typically provides service configuration, service management, service reporting, remote management access, customer SSL certificate management, as well as other functions for configured web applications. The software executing in the branch offices provides last mile web acceleration for users located there. The CDN itself typically provides CDN hardware hosted in CDN data centers to provide a gateway between the nodes running behind the customer firewall and the service provider's other infrastructure (e.g., network and operations facilities). This type of managed solution provides an enterprise with the opportunity to take advantage of CDN technologies with respect to their company's intranet. This kind of solution extends acceleration for the enterprise to applications served anywhere on the Internet, such as SaaS (Software-As-A-Service) applications. By bridging an enterprise's CDN-based private overlay network with the existing CDN public internet overlay network, an end user at a remote branch office obtains an accelerated application end-to-end.

The CDN may have a variety of other features and adjunct components. For example the CDN may include a network storage subsystem (sometimes referred to herein as “NetStorage”) which may be located in a network datacenter accessible to the CDN servers, such as described in U.S. Pat. No. 7,472,178, the disclosure of which is incorporated herein by reference. The CDN may operate a server cache hierarchy to provide intermediate caching of customer content; one such cache hierarchy subsystem is described in U.S. Pat. No. 7,376,716, the disclosure of which is incorporated herein by reference.

For live streaming delivery, the CDN may include a live delivery subsystem, such as described in U.S. Pat. No. 7,296,082, and U.S. Publication No. 2011/0173345, the disclosures of which are incorporated herein by reference.

As noted above, when a given content server in a CDN (or in another distributed computing platform) receives a content request, it typically needs to have information about the identity and characteristics of the requested objects, as well as information about the features of the CDN that should be invoked when delivering those objects. In short, the CDN (and by extension its constituent servers) needs to have information about how to handle a content request. Such information, referred to as “metadata,” can be distributed in configuration files to the content servers, as noted above with respect to U.S. Pat. No. 7,240,100.

However, as a CDN grows and its feature set diversifies, the volume and complexity of metadata rises significantly. Moreover, the continuing move to cloud providers, platform as a service (PaaS), infrastructure as a service (IaaS), and/or software as a service (SaaS), further complicates the management of metadata for a CDN. Improved approaches for delivering and managing metadata are necessary to meet such challenges.

SUMMARY

Described herein are improved methods, devices, and systems for delivering and managing metadata in a distributed computing platform such as a content delivery network (CDN). The teachings hereof provide, among other things, scalable and configurable solutions for delivering and managing metadata, preferably by leveraging dynamically obtained control information. For example, in one embodiment, a given CDN content server may receive and store metadata (e.g., in a configuration file). The metadata can contain references to dynamic, late-bound control information for use in satisfying dependencies in the metadata. This dynamic control information is preferably requested by the CDN content server when needed to parse and execute the metadata, and in many cases (though without limitation) from a remote host at the time of the client request for an object. The dynamic control information may be parameters, e.g., an input to a function in the metadata configuration file. The dynamic control information may be functions or logic. In this way the dynamic control information represents a layer of abstraction within the metadata configuration file. The retrieved dynamic control information may be cached locally for use in handling subsequent requests. A variety of further details, uses and alternatives are described in this document.

By way of further illustration, in an embodiment, an apparatus can comprise a content delivery network (CDN) server that has circuitry forming one or more processors and memory holding instructions to be executed by the one or more processors. The execution of the instructions can cause the CDN server to receive a request for particular content from a client, the request including a host header; determine that a string in the host header is associated with a content control within a set of content controls stored at the CDN server. The content control has at least one dependency. The CDN server can send a request to a remote host for control information that will satisfy the dependency; receive the control information; and satisfy the at least one dependency with the control information. Further, the CDN server can apply the content control prior to serving a response to the request.

In some cases, the executed instructions can cause the CDN server to cache the control information at the CDN server for use with subsequent requests for the particular content, and/or to send a content realm identifier (e.g., extracted from the client request) to the remote host with the request for control information. The content realm identifier can correspond, for example, to a given cloud-customer of the cloud-provider, the cloud-provider being a customer of the CDN and providing a service that is at least one of: infrastructure as a service, platform as a service, software as a service.

In some cases, the content control can include a function that takes at least one parameter as an input, and the control information includes the at least one parameter, and/or determines whether the particular content is valid to serve to the client from a cache at the CDN server. The content control may be in a markup language file, in some cases.

In another embodiment, a system can have a content delivery network (CDN) server that has circuitry forming one or more processors and memory holding instructions to be executed by the one or more processors to cause the CDN server to receive a request for particular content from a client, the request including a host header; determine that a string in the host header is associated with a content control within a set of content controls stored at the CDN server, where the content control has at least one dependency; send a request to a remote host for control information that will satisfy the dependency, the request including one or more pieces of data derived from the request; receive the control information; satisfy the at least one dependency with the control information; and apply the content control prior to serving a response to the request.

The system can also have a remote host for the control information that includes circuitry forming one or more processors and memory holding instructions to be executed by the one or more processors to cause the remote host to: receive the request for the control information from the CDN server; retrieve a control file associated with the control information; execute logic embedded in the control file, the logic taking the one or more pieces of data as parameters and returning control information; and send the control information to the CDN server.

The subject matter described herein has a wide variety of applications in content delivery and online platform architectures.

As those skilled in the art will recognize, the foregoing description merely refers to certain examples of the invention for overview purposes. It is not limiting and the teachings hereof may be realized in a variety of systems, methods, apparatus, and non-transitory computer-readable media. It should also be noted that the allocation of functions to particular machines is not limiting, as the functions recited herein may be combined or split amongst different machines in a variety of ways.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings hereof will be more fully understood from the following detailed description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a schematic diagram illustrating one embodiment of a known distributed computer system configured as a content delivery network;

FIG. 2 is a schematic diagram illustrating one embodiment of a machine in the system of FIG. 1;

FIG. 3 is a schematic diagram illustrating one embodiment of an architecture for communicating metadata control information;

FIG. 4 is a schematic diagram illustrating one embodiment of an architecture for communicating metadata control information;

FIG. 5 is a diagram illustrating one embodiment of a logical flow within a CDN server;

FIG. 6 is a diagram illustrating an embodiment of system in which the remote host evaluates logic in a content policy document to determine control information to return; and,

FIG. 7 is a block diagram illustrating hardware in a computer system that may be used to implement the teachings hereof.

DETAILED DESCRIPTION

The following description sets forth embodiments of the invention to provide an overall understanding of the principles of the structure, function, manufacture, and use of the methods and apparatus disclosed herein. The systems, methods and apparatus described herein and illustrated in the accompanying drawings are non-limiting examples; the scope of the invention is defined solely by the claims. The features described or illustrated in connection with one exemplary embodiment may be combined with the features of other embodiments. Such modifications and variations are intended to be within the scope of the present invention. All patents, publications and references cited herein are expressly incorporated herein by reference in their entirety. Throughout this disclosure, the term ‘e.g.’ is used as an abbreviation for the non-limiting phrase ‘for example’.

INTRODUCTION

Content delivery can be provided by directing client requests for content (e.g., objects such as markup language files, images, scripts, CSS, streaming media, and the like) to the content delivery network—or more particularly, to one of the CDN's constituent servers. When the CDN receives client requests for content, it typically needs to have information about the identity and characteristics of the requested objects, as well as information about the features of the CDN platform that should be invoked when delivering those objects. In short, the CDN (and by extension its constituent servers) needs to have information about how to handle a content request.

This information is referred to herein to as “metadata.” Metadata may include data about the content provider's objects, and more generally may include the set of all control options and parameters that determine how a given CDN server will handle a request for an object (be it an HTML file, images, CSS, scripts, streaming media, or other digital content). For example, a given object may have metadata associated with it that reflects such things as:

CP Code—an internal tracking number, primarily used for billing;

Origin Server—the location of the original copy of the object which a CDN server may need to fetch or revalidate the object (e.g., a content provider's server or NetStorage);

Coherence information—information such as a time-to-live (TTL) indicating how long CDN servers should cache the object before going to the origin server; this maintains the object's freshness.

Metadata may also specify that certain features of the CDN should be invoked when handling the request, and how to do so. These features may range from the use of certain routing technologies or cache-hierarchy-parent, to the modification of the content before serving it (e.g., particular web content optimizations or device-specific adaptations), to the selective invocation of redirect responses, to the application of certain security procedures (e.g., a web application firewall) to content posted from the client. These are merely examples.

As a CDN grows and its feature set diversifies, the volume and complexity of metadata rises significantly. Moreover, the continuing move to cloud providers, such as providers of platform as a service (PaaS), infrastructure as a service (IaaS), and/or software as a service (SaaS), further complicates the management of metadata for a CDN.

For example, a CDN may have as a customer a cloud-provider who is offering a cloud-based service to its own cloud-customers (or in other words, to the ‘cloud-users’). For purposes of illustration, assume the cloud-based service enables each cloud-customer to host their web sites on the cloud-provider platform. The cloud-provider then works with the CDN to have the CDN actually deliver the content from the hosting platform. From the CDN's perspective there is one direct customer relationship with the cloud-provider. However, that cloud-provider may want to have the ability to independently configure at least some or potentially all of its direct cloud-customer sites, be it for internal operational purposes or to be able to pass on a level of customization to its cloud-customers.

As an illustration, consider a cloud-provider who is a SaaS and offers a web application to its cloud-customers. The SaaS provider may want to configure its web application differently for each cloud-customer, again with the content being delivered by the CDN on behalf of the SaaS provider.

Consider further the case of a more traditional content-provider as described previously, but who desires dozens, hundreds, or even thousands of unique websites or other digital properties due the scale of their online operations. A single configuration will likely not suffice—as there will likely be a need for many different configurations for this one content-provider customer of the CDN.

With the foregoing by way of introduction, described below are embodiments of improved metadata systems and methods that address these and similar issues, and provide other functionality as will become clearer below.

Example Infrastructure

FIG. 3 illustrates one embodiment of a metadata infrastructure. Assume—for illustrative purposes only—that a given cloud-provider is a customer of a CDN for delivery and the cloud-provider has many cloud-customers who use its services and by extension those of the CDN, similar to the first example given in the Introduction. Assume further that a given cloud-customer's site can be accessed via the following hostname:

cloud-customer.cloud-provider.com

(This is merely an example. The cloud-customer's hostname could equally well be the name ‘www.cloud-customer.com’ which is aliased, e.g., via CNAME, to the ‘cloud-provider.com’ domain, but the hostname above provides a suitable example for illustrative purposes.)

Assume further that a user operating a client device 308 seeks content at that hostname. The client device 308, running a client application such as a browser, initiates a DNS lookup on the hostname cloud-customer.site.cloud-provider.com, which is aliased (e.g., CNAME) to a CDN domain, and thus through a CDN name service the client device 308 given the address of a particular CDN server 302. This can all be done in the manner described previously and in U.S. Pat. No. 6,108,703, incorporated herein by reference.

The client device 308 sends a content request (e.g., an HTTP ‘Get’) to the CDN server 302 with a hostname header of cloud-customer.cloud-provider.com. The CDN server 302 locates and binds the request to a metadata configuration file(s) 302 a that it has for the cloud-provider.com domain. This may be done, for example, by the CDN server 302 executing a DNS lookup and examining the CNAME chain to determine the CDN customer and customer identifier to use, for example as described in U.S. patent application Ser. No. 13/666,068, filed Nov. 1, 2012 and titled “Multi-domain configuration handling in an edge network server” (now published as 2013/0191499), the teachings of which are hereby incorporated by reference in their entirety.

The metadata configuration file 302 a, which in one embodiment is an XML file, can contain certain (invariant) functions and possibly certain parameters used by those functions, as known in the art and described in U.S. Pat. No. 7,240,100, and it may be periodically be distributed and updated at the CDN server 302 as described therein (prior to being needed for client requests). However, the metadata configuration file 302 a (sometimes referred to as ‘static’ or ‘invariant’ control data) can also contain references to dynamic, late-bound parameters for use in the metadata functions. These parameters are preferably obtained by the CDN server 302 when needed to parse and execute the metadata configuration file 302 a (e.g., at the time of the client request). It should be noted that the approach is not limited to injected parameter values for use in defined functions. In some cases, the injected information can represent certain metadata functions or logic. For convenience of description, all such kinds of dynamic information will be generally referred to herein as dynamic control information 302 b. The dynamic control information 302 b represents a layer of abstraction within the metadata configuration file 302 a.

By way of illustration, consider a metadata function in the configuration file 302 a that checks the HTTP referrer header of an incoming request against a white-list of permitted referrers. The function might be a regular expression match run (by the CDN server 302) on the referrer header against the whitelist, e.g., expressed in XML. Rather than hard-coding the whitelist into the metadata configuration file 302 a, the whitelist is declared as a parameter whose value(s) must be retrieved by the CDN server to evaluate the function. This is but one example of the concept.

As noted above, the CDN server 302 is responsible for obtaining the required late-bound dynamic control information 302 b from a remote host 304. In one embodiment, before processing the request, the CDN server 302 invokes an intermediate processing routine that parses the metadata configuration file 302 a, determines the data dependencies, and obtains and injects the necessary dynamic control information 302 b to fulfill these dependencies in the metadata configuration file 302 a.

As shown in FIG. 3, in one embodiment, the CDN server 302 makes a call, e.g., a service provider interface (SPI) call, to a remote host 304 to obtain the requisite dynamic control information 302 b. As those skilled in the art will recognize, the SPI means that the CDN as the calling party will define the interface specifics, in this embodiment. Thus, in this implementation the remote host 304 may be any system compliant with the SPI, e.g., a system run by the CDN, system run by the CDN customer (the cloud-provider), or even a system run by the cloud-provider's customers (the cloud-customers). In the illustrated embodiment, the remote host 304 is a CDN-operated system in a highly-available platform such as managed network storage facility (aka NetStorage) or otherwise, storing a database 400. The database 400 has the dynamic control information 302 b. The CDN may provide a web-enabled portal 306 a or other user interface through which, for example, a particular cloud-provider and/or cloud provider's cloud-customer can configure or update the database. Alternatively, the cloud-provider may have its own infrastructure 306 b storing its control information which is periodically communicated through an appropriate applications programming interface (API) to the CDN's remote host 304.

Content Realms

Preferably the system 300 utilizes the concept of a ‘content realm’ to manage the retrieval and use of dynamic control information 302 b. The ‘content realm’ defines the context for which the dynamic control information 302 b is being retrieved. Hence, a given CDN customer may be associated with many different defined content realms. If the CDN customer is a cloud-provider, for example, a content realm might be defined for each of the cloud-provider's cloud-customers. For a CDN customer that uses the functionality defined herein to manage several different websites or other digital properties, the content realm might correspond to each site, etc. A content realm could also be associated with a particular area of a site, or with a particular category of products displayed on a given site, and the like.

Preferably, the CDN customer defines the scope and meaning of the content realm. Then, during the processing of a content request from a client device 308, the CDN server 302 determines the content realm identifier (ID) 302 c and passes it via the SPI to the remote host 304, which uses the content realm ID to return the appropriate corresponding set of dynamic control information. In this way, assuming the content realm ID corresponds to a cloud-provider's cloud-customer, the dynamic control information 302 b for the appropriate cloud-customer is retrieved and injected into the metadata configuration file 302 a. FIG. 4 illustrates this process. In FIG. 4, the CDN server 302 makes an SPI request for dynamic control information 302 b consisting of two parameters x, y and sends a content realm ID 302 c with value A, B or C. Assume that the content realm ID 302 c corresponds to a particular cloud-customer. In the database 400, the value of x,y depends on the content realm ID since different cloud-customers may need or desire different content handling features. The remote host 304 looks up the values based on the content realm ID 302 c and returns them to the server 302 for binding to the variables that were declared in the metadata configuration file 302 a.

The CDN server 302 can determine the content realm identifier 302 c in a variety of ways. As mentioned, preferably the CDN customer defines the desired content realm 302 c, and logic for determining the content realm ID 302 c may be included in the control file 302 a. The specific logic to determine the identifier 302 c will be dependent on what it signifies. Preferably the CDN server 302 extracts the content realm ID 302 c from some aspect of the content request transaction/message exchange that occurs between itself and the client device 308. For example, if the identifier 302 c represents a cloud-provider's cloud-customer, the server 302 might extract a content realm identifier 302 c from the host header of the request (e.g., the subdomain “cloud-customer” from “cloud-customer.cloud-provider.com”). The identifier also might come from an intermediate hostname or portion thereof in an DNS aliasing (e.g., CNAMING) chain that the CDN server 302 obtains by performing a DNS lookup on the host header hostname (for example as described in U.S. patent application Ser. No. 13/666,068, filed Nov. 1, 2012 and titled “Multi-domain configuration handling in an edge network server”, now published as U.S. Patent Publication No. 2013/0191499, the contents of which are hereby incorporated by reference). Alternatively, the CDN server 302 might extract the identifier 302 c from the requested universal resource identifier (URI) pathname or other URI component, or from some other HTTP request header. (Note that the term URI used herein includes universal resource locators or URLs.) Hence, the content realm ID might correspond to a product identifier in the URI pathname (e.g., objects under/pathfoo/products1/* being identified as a different content realm, and thus controlled by different dynamic control information, than objects under/pathfoo/products2/*). The content realm ID 302 c might be derived from the user agent, such that a client Windows machine matches to a different content realm, and thus warrants different dynamic control information 302 b, than a client machine running another operating system, for example.

FIG. 5 illustrates, in one embodiment and at a high level, the logical flow within a CDN server 302 to effect the late-binding of control information as described above. In FIG. 5, at step 501 the CDN server 302 receives the client request. At 502, the CDN server binds the request to a metadata configuration file (e.g., based on the host header, which is associated with a particular CDN customer, as previously described with reference to U.S. Pat. No. 7,240,100 and/or US Patent Publication No. 2013/0191499). At 503, the CDN server 302 parses the metadata configuration file 302 a to determine dependencies on dynamic control information, and at 504 determines the content realm ID. At 505 and 506, the CDN server 302 requests the needed dynamic control information from the remote host 304 using the content realm ID and receives back the dynamic control information, caching it locally for future use. At 507, the CDN server 302 constructs the complete metadata configuration file and then (508) processes the client request in accordance therewith.

Caching

Fetched dynamic control information 302 b is preferably cached locally at the CDN server 302 after it is received from the remote host 304. Thus, in one embodiment, the CDN server 302 will pull needed dynamic control information 302 b from the remote host 304 the first time that a client request necessitates it. For example, the information 302 b needed to respond to a request for a particular HTML file will be retrieved and cached (note that the control information needed to handle requests for embedded objects in the HTML file, and/or for other likely-to-be-requested HTML files, might be pre-fetched at the same time). For subsequent requests by the same or another client device 308, the CDN server 302 can use the locally cached information. The local cache entries can be associated with a time-to-live (TTL) so that the CDN server 302 periodically refreshes dynamic control information 302 b.

Local caching does not require storing dynamic control information 302 b for all objects or for all parties served by the CDN. Rather, the CDN server 302 preferably retrieves only the dynamic control information 302 b necessary to respond to the particular client content requests that it is receiving, caching the data 302 b as space permits and evacuating old entries the cache with a least-recently-used or other cache-management algorithm. The CDN server 302 is typically one of many in the CDN and typically sees some portion of the overall traffic. This means that mapping and load-balancing algorithms implemented with the CDN, which spread client content request load amongst various CDN servers 302 in the platform, will concomitantly result in spreading the ‘load’ of requesting and storing dynamic control information 302 b, and provide a scalable solution for the metadata control infrastructure. Put another way, in a preferred embodiment, the load for dynamic control information 302 b will follow load for client content requests.

For example, U.S. Pat. No. 6,108,703 describes in one embodiment a method for intelligently routing and replicating content over a large network of distributed servers. The teachings of U.S. Pat. No. 6,108,703 are hereby incorporated by reference in their entirety.

The foregoing is by way of example only. Any mapping, traffic-shaping, load-balancing or similar policy in the network can be leveraged. Further, it should be noted that it is possible to impose a policy for the dynamic control information 302 b that differs from the policies in place for the client content requests (e.g., it may be desirable in certain situations to push or pre-populate dynamic control information 302 b to certain regions of CDN servers in a way that is not related to how objects are distributed).

Purge Example

In one embodiment, the system 300 can be used to purge “on-demand” objects cached in the CDN servers. Purging objects involves invalidating them (e.g., marking their TTL as ‘expired’) so that they are not served from the CDN server's cache in response to client requests but instead are retrieved from the origin/source server, thus refreshing the cache.

For example, for a given content request for a particular object, the CDN server 302 can execute an ‘invalidate’ function defined in the associated metadata configuration file 302 a. The function can determine whether the requested content should be purged and depends on a late-bound parameter from the remote host 304. In this way the purge function can be, at least in one embodiment, accomplished selectively and quickly, as it will take effect once the database on the remote host 304 is updated.

In one implementation, a function in the metadata configuration file 302 a takes as a parameter an identifier for an object or set of objects (e.g., the identifier may be a URI pointing to a specific object or a path with wildcard/pathfoo/* covering objects in that path) and sets the TTL of the identified object(s) to be ‘expired.’ The late-bound parameter is pulled from the remote host 304. The remote host 304 responds with the particular URI, causing the function to set the objects cached under the particular returned URI to ‘expired.’ This technique can be used to purge not only the requested object but other objects at the same time.

In another implementation, the function in the metadata configuration file 302 a expects a Boolean true/false and sets the TTL of the requested object to ‘expired’ (or not) depending on the answer. The CDN server 302 sends a content realm ID 302 c to the remote host 304 comprising an object URI or other identifier. The remote host 304 looks the object URI (or other identifier) up among URIs (or other identifiers) that have been designated in the database 400 for purging, and returns ‘true’ if a match is found.

These are just two of a variety of possible implementations and are provided merely for illustrative purposes.

Logging of SPI Traffic

Referring to FIG. 3, in one embodiment, the traffic for dynamic control information 302 b that flows between the CDN server(s) 302 and the remote host 304 can be logged, measured and used for billing purposes. Hence, the more complex the configuration for a particular customer's websites and other digital properties, the more they might be charged.

Multi-Dimensional Control & Evaluative Logic at Remote Host

In an alternate embodiment, the dynamic control information 302 b at the remote server 304 is embodied in a content policy document with embedded logic that enables the remote host 304 to return, for a given content realm ID 302 c, different answers that depend on other data that the CDN server 302 sends with the SPI request. This additional layer adds a further dimension of control to the infrastructure.

FIG. 6 illustrates an example. Assume that, as a result of a client content request (e.g., as shown in FIG. 3), the CDN server 302 makes an SPI request for dynamic control information 302 b (a single parameter ‘x’, in this example) and sends a content realm ID 302 c, as well as other data (referred to in this example and in FIG. 6 as a ‘dimension ID’ 302 d). Though the dimension ID 302 d could represent any piece of information, it is often something that is derived from the content request or some circumstance existing at the time of the request. The content policy document contains a logical layer that matches the given dimension ID 302 d to a bucket/category and then returns the corresponding dynamic control information 302 b for that category. As those skilled in the art will recognize, sets of multiple parameters could be determined and returned in this way.

In one use case, the dimension ID 302 d could be a geographical identifier or country name derived from the client IP address by the CDN server 302. Then, the category could represent a geographical region, allowing a website owner to configure the site to respond differently for different regions, based essentially on data injected into the flow at the CDN server 302. Similarly, the CDN server 302 might inject data about the requesting client device (e.g., its browser, screen size, support for certain software, support for touchscreen, whether it is a mobile device, etc.) as the dimension ID 302 d, which the CDN server 302 can determine based on the user agent or other header in the client's content request. The dimension ID might also be representative of the client's connectivity (e.g., broadband, mobile, etc.) as measured by the CDN server 302 or as otherwise determined.

As shown in FIG. 6, a variety of logic and functionality can be included in the policy document. This logic is evaluated by the remote host, taking the inputted data (the dimension ID(s) and returning control information 302(b).

More than one dimension ID 302 d is possible, resulting in a rich set of configuration options.

Computer Based Implementation

The subject matter described herein may be implemented with computer systems, as modified by the teachings hereof, with the processes and functional characteristics described herein realized in special-purpose hardware, general-purpose hardware configured by software stored therein for special purposes, or a combination thereof.

Software may include one or several discrete programs. A given function may comprise part of any given module, process, execution thread, or other such programming construct. Generalizing, each function described above may be implemented as computer code, namely, as a set of computer instructions, executable in one or more microprocessors to provide a special purpose machine. The code may be executed using conventional apparatus—such as a microprocessor in a computer, digital data processing device, or other computing apparatus—as modified by the teachings hereof. In one embodiment, such software may be implemented in a programming language that runs in conjunction with a proxy on a standard Intel hardware platform running an operating system such as Linux. The functionality may be built into the proxy code, or it may be executed as an adjunct to that code.

While in some cases above a particular order of operations performed by certain embodiments is set forth, it should be understood that such order is exemplary and that they may be performed in a different order, combined, or the like. Moreover, some of the functions may be combined or shared in given instructions, program sequences, code portions, and the like. References in the specification to a given embodiment indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic.

FIG. 7 is a block diagram that illustrates hardware in a computer system 700 on which embodiments of the invention may be implemented. The computer system 700 may be embodied in a client device, server, personal computer, workstation, tablet computer, wireless device, mobile device, network device, router, hub, gateway, or other device.

Computer system 700 includes a processor 704 coupled to bus 701. In some systems, multiple processor and/or processor cores may be employed. Computer system 700 further includes a main memory 710, such as a random access memory (RAM) or other storage device, coupled to the bus 701 for storing information and instructions to be executed by processor 704. A read only memory (ROM) 708 is coupled to the bus 701 for storing information and instructions for processor 704. A non-volatile storage device 706, such as a magnetic disk, solid state memory (e.g., flash memory), or optical disk, is provided and coupled to bus 701 for storing information and instructions. Other application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or circuitry may be included in the computer system 700 to perform functions described herein.

Although the computer system 700 is often managed remotely via a communication interface 716, for local administration purposes the system 700 may have a peripheral interface 712 communicatively couples computer system 700 to a user display 714 that displays the output of software executing on the computer system, and an input device 715 (e.g., a keyboard, mouse, trackpad, touchscreen) that communicates user input and instructions to the computer system 700. The peripheral interface 712 may include interface circuitry and logic for local buses such as Universal Serial Bus (USB) or other communication links.

Computer system 700 is coupled to a communication interface 716 that provides a link between the system bus 701 and an external communication link. The communication interface 716 provides a network link 718. The communication interface 716 may represent an Ethernet or other network interface card (NIC), a wireless interface, modem, an optical interface, or other kind of input/output interface.

Network link 718 provides data communication through one or more networks to other devices. Such devices include other computer systems that are part of a local area network (LAN) 726. Furthermore, the network link 718 provides a link, via an internet service provider (ISP) 720, to the Internet 722. In turn, the Internet 722 may provide a link to other computing systems such as a remote server 730 and/or a remote client 731. Network link 718 and such networks may transmit data using packet-switched, circuit-switched, or other data-transmission approaches.

In operation, the computer system 700 may implement the functionality described herein as a result of the processor executing code. Such code may be read from or stored on a non-transitory computer-readable medium, such as memory 710, ROM 708, or storage device 706. Other forms of non-transitory computer-readable media include disks, tapes, magnetic media, CD-ROMs, optical media, RAM, PROM, EPROM, and EEPROM. Any other non-transitory computer-readable medium may be employed. Executable code may also be read from network link 718 (e.g., following storage in an interface buffer, local memory, or other circuitry). 

1.-23. (canceled)
 24. A method for handling client requests at a content delivery network (CDN) server, the CDN server having circuitry forming one or more processors and memory holding instructions to be executed by the one or more processors to perform the method, the method comprising: receiving a request for an object from a client, the request being an HTTP request; in response to the request for the object, binding the request to a metadata configuration file, the metadata control file comprising content handling information to be applied by the CDN server in handling the request; determining, at the time of the request, that the metadata control file includes a reference to particular dynamic control information, the particular dynamic control information comprising any of: a parameter value and a function; in response to said determination, and at the time of the request, retrieving the particular dynamic control information from a remote host, retrieve the particular dynamic control information from a remote host, said retrieving comprising (i) sending the remote host a content realm identifier, the content realm identifier being determined by logic in the metadata control file defined by a CDN customer, the content realm identifier corresponding to a customer of the CDN customer and (ii) receiving the particular dynamic control information from the remote host in response thereto; constructing a complete metadata configuration file by satisfying one or more dependencies in the metadata control file with the particular dynamic control information received from the remote host; processing the request using the completed metadata control file, and transmitting the object to the client in response to the request; locally caching the object; and, locally caching the particular dynamic control information.
 25. The method of claim 1, wherein the server locally caches the particular dynamic control information with a time to live (TTL) value.
 26. The method of claim 1, further comprising evacuating the particular dynamic control information from a local cache in accordance with a cache-management algorithm.
 27. The method of claim 1, further comprising: using the locally cached particular dynamic control information for one or more subsequent requests for the object.
 28. The method of claim 1, wherein the completed metadata control file with the particular dynamic control information determines whether the object is valid to serve to the client.
 29. The method of claim 1, wherein a CDN service provider operates the CDN server as a service for a cloud-provider, the cloud-provider being at least one of a: IaaS provider, PaaS provider, SaaS provider, and the content realm identifier corresponds to a cloud-customer of the cloud-provider.
 30. An apparatus for handling client requests at a content delivery network (CDN) server, the apparatus comprising: a CDN server having circuitry forming one or more processors and memory holding instructions to be executed by the one or more processors, the instructions comprising instructions that, upon execution, cause the CDN server to: receive a request for an object from a client, the request being an HTTP request; in response to the request for the object, bind the request to a metadata control file, the metadata control file comprising content handling information to be applied by the CDN server in handling the request; determine, at the time of the request, that the metadata control file includes a reference to particular dynamic control information, the particular dynamic control information comprising any of: a parameter value and a function; in response to said determination, and at the time of the request, retrieve the particular dynamic control information from a remote host, said retrieving comprising (i) sending the remote host a content realm identifier, the content realm identifier being determined by logic in the metadata control file defined by a CDN customer, the content realm identifier corresponding to a customer of the CDN customer and (ii) receiving the particular dynamic control information from the remote host in response thereto; construct a complete metadata control file by satisfying one or more dependencies in the metadata control file with the particular dynamic control information; process the request in accordance with the complete metadata control file, and transmit the object to the client in response to the request; locally cache the object; and, locally cache the particular dynamic control information.
 31. The apparatus of claim 30, wherein the metadata control file with the particular dynamic control information comprise one or more directives that, upon execution, cause the CDN server to: locally cache the particular dynamic control information with a time to live (TTL) value.
 32. The apparatus of claim 30, wherein the metadata control file with the particular dynamic control information comprise one or more directives that, upon execution, cause the CDN server to: evacuate the particular dynamic control information from a local cache in accordance with a cache-management algorithm.
 33. The apparatus of claim 30, wherein the metadata control file with the particular dynamic control information comprise one or more directives that, upon execution, cause the CDN server to: use the locally cached particular dynamic control information with one or more subsequent requests for the object.
 34. The apparatus of claim 30, wherein the completed metadata configuration file determines whether the object is valid to serve to the client from a local cache.
 35. The apparatus of claim 30, wherein a CDN service provider operates the CDN server as a service for a cloud-provider, the cloud-provider being at least one of a: IaaS provider, PaaS provider, SaaS provider, and the content realm identifier corresponds to a cloud-customer of the cloud-provider. 